Project Title & Description
Project Title: Personal Development Portfolio: UX/UI Design
Design a prototype to identify a flaw within the university’s mobile app, GETmobile. The final version will be a professional portfolio showcasing the process and an interactive Figma prototype.
Vision, Mission, & Strategy Alignment
Personal Mission Connection: This project reflects my mission to “dedicate myself to gaining technical and analytical skills.” It will allow me to gain technical skills like Figma and prototyping, and analytical skills such as user research, to build my future by developing skills that prove my capability.
Vision Alignment: Creating a professional portfolio gives me an idea of what it is like to work in the tech industry to solve real-life problems. It also allows me to make myself a stronger job applicant.
Strategic Goal Support: This project helps me to achieve one of my strategic goals:
- Improve technical skills: This project is basically a hands-on tutorial. I will watch videos and actively use Figma to build a prototype.
Business Case & Justification
Professioanl Value:
- Skills Gained: I will graduate with new skills in user research, prototyping, and usability testing, complementing my CIS degree.
- Improving My Portfolio: This portfolio shows employers that I can apply my knowledge to real-life problems and deliver an outcome.
Personal Value:
- Clarity: It provides an example of exploring a potential career path, reducing the overwhelming options in the tech field.
Learning Outcome:
- Technical skills: Figma proficiency, prototyping, and portfolio development.
- Industry Knowledge: Gaining an understanding of user-centered design processes and how they incorporate with technology
High-Level Scope
In Scope for Semester-Long Project
- Write a short report regarding the survey I put out on the app’s most significant problems.
- Pull out one problem that classmates often mention in the survey
- Create a simple plan of multiple solutions
- Create a prototype on Figma that will fix the issue
- Collect feedback from testing the prototype with a few classmates, and write a report on that
- Create an online portfolio page displaying the project
Roadmap Items - Up to 6 Months After Semester Ends
- Expanding the prototype to include other things besides fixing the issue that I fixed
- Creating a second round of user testing
- Creating a style guide to ensure consistency for all screens.
- Incorporating code such as HTML
Out of Scope
- Building up a real app that we can download
- Releasing the app on the Apple App Store or the Google Play Store
- Fixing the entire GETmobile app
- Collecting data from hundreds of people
5. Stakeholder Register
Stakeholder Identification
| Stakeholder | Catergory | Role/Interest | Power | Interest | Engagement Strategy |
|---|---|---|---|---|---|
| Me | Internal | Lead the project, ensuring it meets all requirements | High | High | Manage closely - Create a schedule and document my progress |
| Professor | Internal | Evaluate the project and give a grade | High | High | Manage closely - Submit drafts for feedback and make sure they follow the guidelines |
| Users | External | Primary users of the app | Medium | High | Keep Informed - Distribute surveys and create user testing |
| University IT | External | Owns and maintains the app | High | Low | Keep Satisfied - Send my ideas as a suggestion |
| Dean of Students | External | Ensures students are satisfied | High | Low | Monitor - They are not engaged in this; the case can be shared with them as an example |
| Associated Students Inc (ASI) | External | Advocates for student needs | Medium | Medium | Keep Informed - Share a summary of the survey and prototype; they could provide more ideas that align with the students. |
| Employeers | External | Will be seeing the portfolio | Medium | Low | Keep Satisfied - Make portfolio case public and professional |
| CIS students | Internal | Can offer feedback | Low | Medium | Keep Informed - Quick feedback on design and prototypes. |
Power-Interest Grid Visual:
Keep Statsfied
(High Power, Low Interest)
- University IT
- Dean of Students
Manage Closely
(High Power, High Interest)
- Me
- Professor
Monitor
(Low power, Low Interest)
- Employers
- CIS Students
Keep Informed
(Low Power, High Interest)
- Users
- Associated Students Inc
6. Deliverables and Work Breakdown Structure
| WBS ID | Level | Task/Work Package Name | Duration | Dependencies (WBS ID & Name) |
|---|---|---|---|---|
| 1 | Deliverble | Project Brief & Problem Statement | 09/26/25 | |
| 1.1 | Work Package | User Research & Data Collection | 09/22/25 | |
| 1.1.1 | Task | Draft Survey Questions | 09/19/25 | |
| 1.1.2 | Task | Distribute survey via Qualtrics | 09/19/25 | 1.1.1 - Draft Survey Questions |
| 1.1.3 | Task | Monitor responses and close survey | 09/21/25 | 1.1.2 - Distribute survey wuestions |
| 1.2 | Work Package | Data Analysis | 09/21/25 | 1.1 User Research & Data collection |
| 1.2.1 | Task | Complie survey results into a spreadsheet | 09/19/25 | 1.1.3 Monitor responses and close survey |
| 1.2.2 | Task | Identify top three issues | 09/20/25 | 1.2.1 Complie survey results into spreadsheet |
| 1.2.3 | Task | Select the most common problem | 09/19/25 | 1.2.2 Identify top three issues |
| 1.3 | Work Package | Create document | 09/22/25 | 1.2 Data Analysis |
| 1.3.1 | Task | Write Problem Statement | 09/19/25 | 1.2.3 Select the most common problem |
| 1.3.2 | Task | Create visuals of survey data | 09/20/25 | 1.2.1 Complie survey results into a spreadsheet |
| 1.3.3 | Task | Write one page brief in Google Docs | 09/20/25 | 1.3.1 Write Problem Statement ||1.3.2 Create visuals of survey data |
| 1.3.4 | Task | Export brief as PDF | 09/19/25 | 1.3.3 Write one page brief in Google Docs |
| 2 | Deliverble | Current User Map | 09/23/25 | 1.0 Project Brief & Problem Statement |
| 2.1 | Work Package | Document the app flow | 09/20/25 | 1.3.4 Export brief as PDF |
| 2.1.1 | Task | Perform task in the app, taking screenshots | 09/19/25 | |
| 2.1.2 | Task | List user action in Google Docs | 09/20/25 | 2.1.1 Perform task in the app, taking screenshots |
| 2.2 | Work Package | Build Map | 09/21/25 | 2.1 Document the app flow |
| 2.2.1 | Task | Choose tool like FigJam | 09/19/25 | |
| 2.2.2 | Task | Put together screenshots and timeline | 09/20/25 | 2.2.1 Choose tool ||2.1.1 Taking Screenshots |
| 2.2.3 | Task | Add notes to highlight top three issues | 09/19/25 | 2.2.2 Put together screenshots ||2.1.2 List user action |
| 2.2.4 | Task | Export map as PDF | 09/19/25 | |
| 3 | Deliverable | Prototype | 7 days | 2.0 Current User Map |
| 3.1 | Work Package | Low-Fidelity Design | 3 days | 2.0 Current User Map |
| 3.1.1 | Task | Put together 3 ideas for new user flow | 1 day | 2.2.4 Export map as PDF |
| 3.1.2 | Task | Select best solution out of three | 1 hour | 3.1.1 3 Ideas |
| 3.1.3 | Task | Create wireframe in Figma | 4 days | 3.1.2 Best Solution |
| 3.2 | Work Package | High-Fidelity Visual Design | 4 days | 3.1 Low-Fidelity Design |
| 3.2.1 | Task | Determine visual style guide (colors, font) | 1 day | 3.1.3 Create wireframe |
| 3.2.2 | Task | Create reusable UI components (buttons etc) | 3 days | 3.2.1 Visual style guide |
| 3.3 | Work Package | Protoype and review | 4 days | 3.2 High-Fidelity |
| 3.3.1 | Task | Conduct review with class peers | 2 days | 3.2 High-Fidelity |
| 3.3.2 | Task | Make changes based on feedback | 2 days | 3.3.1 Reviews |
| 4 | Deliverable | Test Report | 7 days | 3.0 Prototype |
| 4.1 | Test Preperation | 1 day | 3.0 Prototype | |
| 4.1.1 | Create test script with 3 tasks | 1 hour | 3.3.2 Feedback | |
| 4.1.2 | Ask 3+ classmates as test participants | 1 hour | 4.1.1 Test script | |
| 4.2 | Work Package | Test Exceution | 2 days | 4.1 Test Preperation |
| 4.2.1 | Usablity test session | 2 days | 4.1.2 Test Participants | |
| 4.2.2 | Take notes on user feedback | 1 day | 4.2.1 Test session | |
| 4.3 | Analysis & Report | 1 day | 4.2 Test Exceution | |
| 4.3.1 | Write notes on user feedback into findings | 1 hour | 4.2.2 Notes on user feedback | |
| 4.3.2 | Write one page summary report of findings | 1 day | 4.3.1 Notes into findings | |
| 5 | Deliverable | Portfolio | 5 days | 4.0 Test report |
| 5.1 | Content Creation | 3 days | 4.0 Test report | |
| 5.1.1 | Gather all project materials (PDF, map etc) | 1 day | 4.3.2 Report on findings | |
| 5.1.2 | Write caste study | 2 days | 5.1.1 Materials | |
| 5.2 | Publication | 4 days | 5.1 Content Creation | |
| 5.2.1 | Choose Portfolio platform | 1 hour | ||
| 5.2.2 | Build case study page | 3 days | 5.2.1 Choose Platform || 5.1.2 Case Study | |
| 5.2.3 | Publish page to URL | 1 hour |
7. Budget
| Category / Item | Term / Qty | Unit Cost | Amount |
|---|---|---|---|
| LABOR SUBTOTAL | 4448 | ||
| EQUIPMENT/SOFTWARE | |||
| Figma Pro Plan | 3 months | $16.00 | $48.00 |
| EQUIPMENT/SOFTWARE SUBTOTAL | 48 | ||
| MATERIALS | |||
| Stock Images/Media | 1 | $50.00 | $50.00 |
| MATERIALS SUBTOTAL | 50 | ||
| SERVICES | |||
| Cloud Storage (Google Drive) | 3 months | $19.99 | $59.97 |
| SERVICES SUBTOTAL | 59.97 | ||
| SUBTOTAL DIRECT COSTS | 4,605.97 | ||
| Contingency Reserve (%) | 20% | 921.19 | |
| TOTAL PROJECT BUDGET | 5527.16 | ||
8. Project Methodology Explanation
The diagram shows the four phase: Discover, design and prototype, test, and lastly deliver. It is providing a clear structure for my timeline. The diagram contains two iterative cycles. The first cyle covers:
- Creating wireframe
- Get feedback from classmates
- Go over it until I am satisfied with design
The second cyle covers:
- Test high-fidelity prototype with users
- Analyze data
- Make revisions based on analyzation
Each phases ends with a deliverable as it was outlined on my Work Breakdown Structure sheet. The design visually highlights how feedback is key to the project, leading to revisions and improvements ensuring the final portofolio is perfect.
Project Methodology Diagram
9. Project Tool Selection Explanation
After evaluating three project tool platforms, I decided to proceed with Smartsheet. Even if my methodology is hybrid iterative rather than predictive, Smartsheet is still the best fit for this project. An advantage of selecting this platform is the ability to upload my Excel WBS sheet directly, removing the provess of reentering all of my tasks which can take up alot of my time. Smartsheet is also perfect for my personally since I am not an organized person, a checkbox will not do the job for me. It allows me to view the entire project timeline.
Screenshots
